fix: show actual error cause in harness startup failure dialog - #84
Open
yaojin3616 wants to merge 1 commit into
Open
fix: show actual error cause in harness startup failure dialog#84yaojin3616 wants to merge 1 commit into
yaojin3616 wants to merge 1 commit into
Conversation
When the Harness process exits unexpectedly during startup, users only saw 'exit code 1' with no indication of what actually went wrong. This change extracts the most relevant error from the captured stderr and includes it directly in the failure message, so the dialog shows the actual cause (e.g. plugin load failures, missing modules, config errors) without requiring users to dig into the log file. Closes #77
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the Harness process exits unexpectedly during startup, users only saw "exit code 1" with no indication of what actually went wrong. This change extracts the most relevant error from captured stderr and includes it directly in the failure message.
Changes
extractFailureCause()function that scans log lines for known error patterns (DSH entry failure, uncaught exceptions, unhandled rejections, generic error lines)Issue
Closes #77
Verification